Automated Device Memory Clean Up Mechanism

ABSTRACT

A memory clean up mechanism may dynamically calculate the amount of free memory required and then identify a list of unused applications that may be automatically deleted to reach the required free memory.

TECHNICAL FIELD

The technical field generally relates to installing software and, morespecifically, to systems and methods of managing memory for installingthe software.

BACKGROUND

Software update packages are increasing in size. Device users heavilyutilize the available memory on the device by downloading applicationsand storing pictures or videos. As a result, there is a growing trendtowards insufficient memory conditions on a device for the download andinstallation of an update package. This will cause the software updateto fail and require the user to manually identify and delete downloadedapplications, cache memory, pictures, and videos.

SUMMARY

Disclosed herein is a memory clean up mechanism that may be invoked whena device detects an insufficient memory condition for the download orinstallation of the update package. The memory clean up mechanism maydynamically calculate the amount of free memory required and thenidentify a list of unused applications that may be automatically deletedto reach the required free memory.

In an example, a mobile device may include a processor and a memorycoupled with the processor. The memory may include executableinstructions that when executed by the processor cause the processor toeffectuate operations that include: receiving a notification of anupdate of a first application; determining anticipated amount of memoryallocated for the update of the first application; determining a list ofa plurality of applications based on information, the informationcomprising last use of the plurality of applications in a period;determining the used memory for each application of the plurality ofapplications; provide a list of the used memory for a first subset ofthe plurality of applications; and receiving a selection of a secondsubset of the first subset, wherein the second subset has an amount ofmemory totaling greater than or equal to the anticipated amount ofmemory allocated for the update of the first application.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the herein described telecommunications network and systemsand methods for antenna switching based on device position are describedmore fully with reference to the accompanying drawings, which provideexamples. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide anunderstanding of the variations in implementing the disclosedtechnology. However, the instant disclosure may take many differentforms and should not be construed as limited to the examples set forthherein. When practical, like numbers refer to like elements throughout.

FIG. 1 illustrates an exemplary mobile device that may implement memoryclean-up as discussed herein.

FIG. 2 illustrates an exemplary method for memory clean-up as discussedherein.

FIG. 3 illustrates an exemplary interface associated with deletingtemporary files.

FIG. 4 illustrates an exemplary interface associated with deletingtemporary files.

FIG. 5 illustrates an exemplary use of the other applications button formemory clean-up as discussed herein.

FIG. 6 illustrates an exemplary use of the space indicator of memoryclean-up as discussed herein.

FIG. 7 illustrates an exemplary selection and installation interface ofmemory clean-up as discussed herein.

FIG. 8 illustrates a schematic of an exemplary network device.

FIG. 9 illustrates an exemplary communication system that provideswireless telecommunication services over wireless communicationnetworks.

FIG. 10 illustrates an exemplary communication system that provideswireless telecommunication services over wireless communicationnetworks.

FIG. 11 illustrates an exemplary telecommunications system in which thedisclosed methods and processes may be implemented.

FIG. 12 illustrates an example system diagram of a radio access networkand a core network.

FIG. 13 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a general packet radioservice (GPRS) network.

FIG. 14 illustrates an exemplary architecture of a GPRS network.

FIG. 15 is a block diagram of an exemplary public land mobile network(PLMN).

DETAILED DESCRIPTION

Software update packages are increasing in size. As a result, there is agrowing trend towards insufficient memory conditions on a device for thedownload and installation of an update package. Disclosed herein is anautomated memory clean up mechanism which may be invoked when the devicedetects an insufficient memory condition associated with theinstallation of the update package. The memory clean up mechanism maydynamically calculate the amount of free memory required and thenidentify a list of unused applications that may be automatically deletedto reach the free memory requirement.

FIG. 1 illustrates an exemplary mobile device that may implement memoryclean-up as discussed herein. Mobile device 100 may include interface101 that displays a plurality of features associated with memoryclean-up. The display of interface 101 may be provided in response tomobile device 100 determining that there is insufficient memory toinstall software, which may be a software update or new software. In anexample, the software is an update of a version of software (e.g.,application 110) that is already installed on mobile device 100.Application 110 may include firmware or other applications (e.g.,navigation application or word processing application). Word 102 may bea hyperlinked word “here” that links to a description of features thatare included in the update of application 110.

As shown in FIG. 1, interface 101 displays a list of a plurality ofapplications that are candidates for removal, such as application 111,application 112, application 113, application 114, and application 115.Next to application 111, and the other applications, there is acorresponding memory indicator 108 (e.g., 428 MB) associated withapplication 111 and selection block 103 that is an indication ofselection of application 111 to be removed. Memory indicator 108 may behow much memory available after removal of application 111 (e.g., usedmemory) or the like indicator associated with an amount of memory.Interface 101 may also include space indicator 104. Space indicator 104is a representation of how much space is needed for installation of anupdate of application 110 (e.g., anticipated amount of memory allocatedfor the update of application 110). This anticipated amount may be aminimum amount of memory that needs to be allocated for the applicationto work in a particular manner (e.g., minimal functionality or withadditional features). Space indicator 104 may be decremented when anapplication is selected, such as application 111 corresponding toselection block 103. In addition, interface 101 may include a delaybutton 105, other applications button 106, or remove button 107. Delaybutton 105 may be used to delay the install of the update of application110 to another time when delay button 105 is pressed, or otherwiseselected. Delay button 105 may be pressed at time T1 and an install maybe postponed and at time T2 (e.g., 9 days later) mobile device 100 willindicate the earlier selected applications (time T1). Delay button 105may allow for a particular time of install to be scheduled. Install mayalso be automatic after a certain amount of delays. Other applicationsbutton 106 may be used to find other applications that may not be shown,but are candidates for removal (e.g., uninstallation). Remove button 107may be used to remove selected applications when button 107 is pressed,or otherwise selected. Remove button 107 may remain in an inactive stateuntil the necessary free memory space, as projected by the number ofselected applications and corresponding memory, is greater than or equalto the memory requirement for the update of application 110.

FIG. 2 illustrates an exemplary method for memory clean-up. At block120, a notification of an update of application 110 may be received. Inan example, interface 101, as shown in FIG. 1, may be displayed onmobile device 100. Although not shown, interface 101 may show the nameand other statistics associated with application 110, which is thesoftware to be updated. At block 121, the memory needed to updateapplication 110 is determined. The memory needed may be a part of thenotification in block 120. The memory needed may be determined bycalculating the memory of application 110 on the device (e.g., baseapplication information and game play information), memory for newfeatures, or combination of the aforementioned, among otheralternatives. At block 122, the temporary files may be examined. Mobiledevice 100 may determine that deleting the temporary files will createenough space to install the updated application. In an example, ifdeleting temporary files is sufficient, then there may be no need toinvestigate unused applications any further (e.g., block 123, etc.).Mobile device may just automatically delete the temporary files (e.g.,FIG. 3) and install the application (e.g., block 128). In an alternativeexample, mobile device 100 may list “temporary files” as an option(e.g., another application, such as temporary files 116 of FIG. 4) and auser may decide whether to delete the temporary files 116 orapplications (e.g., application 111 through application 114).

At block 123, applications corresponding to desired information, such asunused applications within a period, are determined. Example period maybe greater than 30 days, 60 days, 90 days, or the like. Some or allapplications may be selected based on other information, such asfrequency of use, location, etc. In another example, applications mayranked by lack of use and then as discussed herein a candidate shortlist may be created and provided. At block 124, the memory of eachunused application of block 123 may be determined.

With continued reference to FIG. 2, at block 125, a list of candidateunused applications may be provided. There may be a candidate list whichis extended. This extended list may be the list presented when otherapplications button 106 is selected (e.g., see FIG. 5). There also maybe an initially shown candidate short list (e.g., see FIG. 1,applications 111 through 115) that shows a truncated candidate list. Forexample, the candidate short list may be selected based on rankdetermined by a result of weighing information as discussed herein, ormay be randomly selected. The candidate list or candidate short list maybe determined by information, such as period applications are unused,restrictions on application 111, memory of application 111, memory spaceneeded, or location, among other information. The information may beused as weighted to help determine what should be in the candidate list,the candidate short list, or the like. With regard to the restriction onapplication 111, in an example, there may be emergency applications(e.g., 911 emergency related), applications associated with a payment tohave priority to remain on mobile device 100, or wireless serviceprovider sponsored applications that have priority to not be removed.With regard to memory of application 111, in an example, thedetermination may be weighted more heavily to applications that take upmore memory, rather than applications than period of use. With regard tolocation information, there may be some applications that may be ofparticular importance in a location. In an example, an application mayhave history of being used in a particular location, so it may not bepresented on the candidate short list if mobile device 100 is at or in athreshold range of the particular location.

At block 126, a subset of the candidate list or the candidate short listis selected to be removed (e.g., deleted or compressed) from mobiledevice 100. When an application is selected, space indicator 104 mayindicate how much more space is needed. For example, as shown in FIG. 1,space indicator 104 provides that there is 826 MB needed when noapplications are selected. In FIG. 6, space indicator 104, shows only 69MB needed after application 111 and application 113 are selected. Itshould be understood that remove button 107 may still be inactive. Thismay be done to help indicate that more memory needs to be freed up forinstallation of the update to application 110. At block 127, theselected subset of the candidate list is deleted and the software isinstalled. FIG. 7 illustrates an exemplary selection of application 112and application 113 and installation message based on the removalselection creating the necessary memory space.

Discussed below are additional considerations with regards to the memoryclean-up as discussed herein. Alternatively, interface 101 may showapplication 110 (the software to be updated) and information (e.g.,statistics). Information may include last use of application 110, thefrequency of use of application 110, or location of use of application110, among other things. In a third scenario, based on the information,mobile device 100 may determine that application 110 meets certainthresholds that recommend that it should not be updated. In addition,mobile device 100 may recommend deleting application 110 or mayautomatically delete application 110 instead of update it. In a fourthscenario, there may be an analysis of the information of application 110and the information of other applications (e.g., the applications unusedin a period—applications 111 through application 115). The result of theanalysis may determine whether interface 101 is displayed or if one ormore steps of memory clean-up should be executed. With regard to thefourth scenario, in an example, if application 110 has not been usedmore often than the list of unused applications in a period, then block121 and block 124 through block 126 may not occur. It is alsocontemplated herein, that based a threshold frequency of use (or otherinformation) of application 110 and threshold frequency us (or otherinformation) of candidate applications, mobile device 100 mayautomatically delete applications to create the necessary memory spacewithout displaying interface 101. Further, it is contemplated thatapplications may be periodically (proactively) marked (e.g., ranked) tobe deleted when there eventually is a lack of memory for updatingapplication 110. For example, a user may rank the applications of mobiledevice 100 to delete at time T1 and at time T2 (e.g., 10 days later),memory may need to be cleaned up. The user may be presented with theranked applications which may supersede rankings based on information,such as unused period of application 111.

The automated memory clean up mechanism disclosed herein may allow forthe following: 1) intelligent calculation of free memory required; 2)intelligent assessment of the list of unused applications which could bewiped; 3) automated delete or wipe of unused applications; 4) remove theneed to manually check the device storage and delete individualapplications; 5) notify a user when the required free memory isavailable; and 6) assist in making sure that a software update does notfail due to insufficient memory, among other things. It is understoodherein that the criteria and methods herein for unused applications(e.g., application 111 through application 115) may application tofiles, such as temporary files 116, among others.

FIG. 8 is a block diagram of network device 300 that may be connected toor comprise mobile device 100. Network device 300 may comprise hardwareor a combination of hardware and software. The functionality tofacilitate telecommunications via a telecommunications network mayreside in one or combination of network devices 300. Network device 300depicted in FIG. 8 may represent or perform functionality of anappropriate network device 300, or combination of network devices 300,such as, for example, a component or various components of a cellularbroadcast system wireless network, a processor, a server, a gateway, anode, a mobile switching center (MSC), a short message service center(SMSC), an ALFS, a gateway mobile location center (GMLC), a radio accessnetwork (RAN), a serving mobile location center (SMLC), or the like, orany appropriate combination thereof. It is emphasized that the blockdiagram depicted in FIG. 8 is exemplary and not intended to imply alimitation to a specific implementation or configuration. Thus, networkdevice 300 may be implemented in a single device or multiple devices(e.g., single server or multiple servers, single gateway or multiplegateways, single controller or multiple controllers). Multiple networkentities may be distributed or centrally located. Multiple networkentities may communicate wirelessly, via hard wire, or any appropriatecombination thereof.

Network device 300 may comprise a processor 302 and a memory 304 coupledto processor 302. Memory 304 may contain executable instructions that,when executed by processor 302, cause processor 302 to effectuateoperations associated with mapping wireless signal strength. As evidentfrom the description herein, network device 300 is not to be construedas software per se.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together (coupling not shown inFIG. 8) to allow communications therebetween. Each portion of networkdevice 300 may comprise circuitry for performing functions associatedwith each respective portion. Thus, each portion may comprise hardware,or a combination of hardware and software. Accordingly, each portion ofnetwork device 300 is not to be construed as software per se.Input/output system 306 may be capable of receiving or providinginformation from or to a communications device or other network entitiesconfigured for telecommunications. For example input/output system 306may include a wireless communications (e.g., 3G/4G/GPS) card.Input/output system 306 may be capable of receiving or sending videoinformation, audio information, control information, image information,data, or any combination thereof. Input/output system 306 may be capableof transferring information with network device 300. In variousconfigurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi,Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, input/output system 306 may comprise aWi-Fi finder, a two-way GPS chipset or equivalent, or the like, or acombination thereof.

Input/output system 306 of network device 300 also may contain acommunication connection 308 that allows network device 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network device 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a nonremovable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to map signal strengths in an area of interest.

FIG. 9 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 that may be used with memoryclean-up of the current disclosure. In particular, the networkarchitecture 400 disclosed herein is referred to as a modified LTE-EPSarchitecture 400 to distinguish it from a traditional LTE-EPSarchitecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. In one embodiment, theLTE-EPS network architecture 400 includes an access network 402, a corenetwork 404, e.g., an EPC or Common BackBone (CBB) and one or moreexternal networks 406, sometimes referred to as PDN or peer entities.Different external networks 406 can be distinguished from each other bya respective network identifier, e.g., a label according to DNS namingconventions describing an access point to the PDN. Such labels can bereferred to as Access Point Names (APN). External networks 406 caninclude one or more trusted and non-trusted external networks such as aninternet protocol (IP) network 408, an IP multimedia subsystem (IMS)network 410, and other networks 412, such as a service network, acorporate network, or the like.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (e-NodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 (e.g.,mobile device 100) can include, without limitation, wireless devices,e.g., satellite communication systems, portable digital assistants(PDAs), laptop computers, tablet devices and other mobile devices (e.g.,cellular telephones, smart appliances, and so on). UEs 414 can connectto eNBs 416 when UE 414 is within range according to a correspondingwireless communication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PGW 426. In oneembodiment, MME 418 comprises a control node performing a controlsignaling between various equipment and devices in access network 402and core network 404. The protocols running between UE 414 and corenetwork 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer pathsand/or interfaces are terms that can include features, methodologies,and/or fields that may be described in whole or in part by standardsbodies such as the 3GPP. It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state, and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), and/or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from one peer entity 406,and triggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, tHSS 422 can store information such as authorizationof the user, security requirements for the user, quality of service(QoS) requirements for the user, etc. HSS 422 can also hold informationabout external networks 406 to which the user can connect, e.g., in theform of an APN of external networks 406. For example, MME 418 cancommunicate with HSS 422 to determine if UE 414 is authorized toestablish a call, e.g., a voice over IP (VoIP) call before the call isestablished. Quality of service is the ability to provide differentpriority to different applications, users, or data flows, or toguarantee a certain level of performance to a data flow. For example, arequired bit rate, delay, jitter, packet dropping probability and/or biterror rate may be guaranteed. Quality of service guarantees areimportant if the network capacity is insufficient, especially forreal-time streaming multimedia applications such as voice over IP,online games and IP-TV, since these often require fixed bit rate and aredelay sensitive, and in networks where the capacity is a limitedresource, for example in cellular data communication

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426. PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an S1-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably, S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring and/or managing packet forwarding betweeneNB 416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory and/or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, and/or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities and/or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 and/or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read and/orwrite values into either of storage locations 442, 444, for example,managing Currently Used Downlink Forwarding address value 442 andDefault Downlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, and/or other data structuresgenerally well understood and suitable for maintaining and/or otherwisemanipulate forwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 9. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches and controllers. In addition, although FIG. 9illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMEs 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a, SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 400, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 9. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., S1signaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes of network 400, e.g.,by one or more of tunnel endpoint identifiers, an IP address and a userdatagram protocol port number. Within a particular tunnel connection,payloads, e.g., packet data, which may or may not include protocolrelated information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S1-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPv1-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. That is,SGW 420 can serve a relay function, by relaying packets between twotunnel endpoints 416 a, 426. In other scenarios, direct tunnelingsolution 458 can forward user data packets between eNB 416 a and PGW426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual bases. That is, if user data packets of one bearer, say abearer associated with a VoIP service of UE 414, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 414 can have another bearer associatedwith it through the same eNB 416 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 404 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 458; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 450.

FIG. 10 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods for memory clean-up as discussed herein. One or more instancesof the machine can operate, for example, as processor 302, mobile device100, UE 414, eNB 416, MME 418, SGW 420, HSS 422, PCRF 424, PGW 426 andother devices. In some embodiments, the machine may be connected (e.g.,using a network 502) to other machines. In a networked deployment, themachine may operate in the capacity of a server or a client user machinein a server-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 11, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise mobile device 100, network device 300, or the like, or anycombination thereof. By way of example, WTRUs 602 may be configured totransmit or receive wireless signals and may include a UE, a mobilestation, a fixed or mobile subscriber unit, a pager, a cellulartelephone, a PDA, a smartphone, a laptop, a netbook, a personalcomputer, a wireless sensor, consumer electronics, or the like. It isunderstood that the exemplary devices above may overlap in theirfunctionality and the terms are not necessarily mutually exclusive.WTRUs 602 may be configured to transmit or receive wireless signals overan air interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 11, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 11, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. That is, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 12 is an example system 400 including RAN 604 and core network 606that may be used with memory clean-up as discussed herein. As notedabove, RAN 604 may employ an E-UTRA radio technology to communicate withWTRUs 602 over air interface 614. RAN 604 may also be in communicationwith core network 606.

RAN 604 may include any number of eNode-Bs 702 while remainingconsistent with the disclosed technology. One or more eNode-Bs 702 mayinclude one or more transceivers for communicating with the WTRUs 602over air interface 614. Optionally, eNode-Bs 702 may implement MIMOtechnology. Thus, one of eNode-Bs 702, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of WTRUs 602.

Each of eNode-Bs 702 may be associated with a particular cell (notshown) and may be configured to handle radio resource managementdecisions, handover decisions, scheduling of users in the uplink ordownlink, or the like. As shown in FIG. 12 eNode-Bs 702 may communicatewith one another over an X2 interface.

Core network 606 shown in FIG. 12 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNode-Bs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 13 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network, that may beused with the systems and methods of memory clean-up as discussed hereinas described herein. In the example packet-based mobile cellular networkenvironment shown in FIG. 13, there are a plurality of base stationsubsystems (BSS) 800 (only one is shown), each of which comprises a basestation controller (BSC) 802 serving a plurality of BTSs, such as BTSs804, 806, 808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a boarder gateway router (BGR) 832. A Remote AuthenticationDial-In User Service (RADIUS) server 834 may be used for callerauthentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 14 illustrates an architecture of a typical GPRS network 900 thatmay be used with memory clean-up as discussed herein. The architecturedepicted in FIG. 14 may be segmented into four groups: users 902, RAN904, core network 906, and interconnect network 908. Users 902 comprisea plurality of end users, who each may use one or more devices 910. Notethat device 910 is referred to as a mobile subscriber (MS) in thedescription of network shown in FIG. 14. In an example, device 910comprises a communications device (e.g., mobile device 100, networkdevice 300, any of detected devices 500, second device 508, accessdevice 604, access device 606, access device 608, access device 610 orthe like, or any combination thereof). Radio access network 904comprises a plurality of BSSs such as BSS 912, which includes a BTS 914and a BSC 916. Core network 906 may include a host of various networkelements. As illustrated in FIG. 14, core network 906 may comprise MSC918, service control point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924,home location register (HLR) 926, authentication center (AuC) 928,domain name system (DNS) server 930, and GGSN 932. Interconnect network908 may also comprise a host of various networks or other networkelements. As illustrated in FIG. 14, interconnect network 908 comprisesa PSTN 934, an FES/Internet 936, a firewall 1038, or a corporate network940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 14, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 15 illustrates a PLMN block diagram view of an example architectureof a telecommunications system that may be used by systems and methodsfor memory clean-up as discussed herein. In FIG. 15, solid lines mayrepresent user traffic signals, and dashed lines may represent supportsignaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, mobile device 100, network device 300, thelike, or any combination thereof may serve as MS 1002. MS 1002 may beone of, but not limited to, a cellular telephone, a cellular telephonein combination with another electronic device or any other wirelessmobile communication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobilephone, wireless router, or other device capable of wireless connectivityto E-UTRAN 1018. The improved performance of the E-UTRAN 1018 relativeto a typical UMTS network allows for increased bandwidth, spectralefficiency, and functionality including, but not limited to, voice,high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically MS 1002 may communicate with any or all of BSS 1004, RNS 1012,or E-UTRAN 1018. In a illustrative system, each of BSS 1004, RNS 1012,and E-UTRAN 1018 may provide MS 1002 with access to core network 1010.Core network 1010 may include of a series of devices that route data andcommunications between end users. Core network 1010 may provide networkservice functions to users in the circuit switched (CS) domain or thepacket switched (PS) domain. The CS domain refers to connections inwhich dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010, and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location information such as,but not limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation information.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from PGW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location information. HSS 1042 may also provide call orsession establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location information to the VLRfor the area. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1028, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station Identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1002registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. A MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

As described herein, a telecommunications system wherein management andcontrol utilizing a software designed network (SDN) and a simple IP arebased, at least in part, on user equipment, may provide a wirelessmanagement and control framework that enables common wireless managementand control, such as mobility management, radio resource management,QoS, load balancing, etc., across many wireless technologies, e.g. LTE,Wi-Fi, and future 5G access technologies; decoupling the mobilitycontrol from data planes to let them evolve and scale independently;reducing network state maintained in the network based on user equipmenttypes to reduce network cost and allow massive scale; shortening cycletime and improving network upgradability; flexibility in creatingend-to-end services based on types of user equipment and applications,thus improve customer experience; or improving user equipment powerefficiency and battery life—especially for simple M2M devices—throughenhanced wireless management.

While examples of a telecommunications system in which emergency alertscan be processed and managed have been described in connection withvarious computing devices/processors, the underlying concepts may beapplied to any computing device, processor, or system capable offacilitating a telecommunications system. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes an device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While a telecommunications system has been described in connection withthe various examples of the various figures, it is to be understood thatother similar implementations may be used or modifications and additionsmay be made to the described examples of a telecommunications systemwithout deviating therefrom. For example, one skilled in the art willrecognize that a telecommunications system as described in the instantapplication may apply to any environment, whether wired or wireless, andmay be applied to any number of such devices connected via acommunications network and interacting across the network. Therefore, atelecommunications system as described herein should not be limited toany single example, but rather should be construed in breadth and scopein accordance with the appended claims.

In describing preferred methods, systems, or apparatuses of the subjectmatter of the present disclosure—memory clean-up—as illustrated in theFigures, specific terminology is employed for the sake of clarity. Theclaimed subject matter, however, is not intended to be limited to thespecific terminology so selected, and it is to be understood that eachspecific element includes all technical equivalents that operate in asimilar manner to accomplish a similar purpose.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art (e.g., skipping steps, combiningsteps, or adding steps between exemplary methods disclosed herein). Suchother examples are intended to be within the scope of the claims if theyhave structural elements that do not differ from the literal language ofthe claims, or if they include equivalent structural elements withinsubstantial differences from the literal languages of the claims.

What is claimed:
 1. A mobile device comprising: a processor; and amemory coupled with the processor, the memory comprising executableinstructions that when executed by the processor cause the processor toeffectuate operations comprising: receiving a notification of an updateof a first application; determining an anticipated amount of memoryallocated for the update of the first application; determining a list ofa plurality of applications based on information, the informationcomprising last use in a period; determining a used memory for eachapplication of the plurality of applications; providing a list of theused memory for a first subset of the plurality of applications; andreceiving a selection of a second subset of the first subset, whereinthe second subset has an amount of memory totaling greater than or equalto the anticipated amount of memory allocated for the update of thefirst application.
 2. The mobile device of claim 1, further operationscomprising deleting the second subset based on receiving the selectionof the second subset.
 3. The mobile device of claim 1, furtheroperations comprising: deleting the second subset based on receiving theselection of the second subset; and in response to deleting the secondsubset, installing the update of the first application.
 4. The mobiledevice of claim 1, further operations comprising based on the selectionof the second subset, displaying a remaining memory to be deleted inorder to update the first application.
 5. The mobile device of claim 1,further operations comprising based on the selection of the secondsubset adding up to the anticipated amount of memory allocated for theupdate of the first application, activating a button for uninstallingthe second subset.
 6. The mobile device claim 1, wherein the informationcomprises location of the mobile device.
 7. The mobile device of claim1, wherein the information comprises frequency of use in the period. 8.A method comprising: receiving, by a mobile device, a notification of anupdate of a first application; determining, by the mobile device, ananticipated amount of memory allocated for the update of the firstapplication; determining, by the mobile device, a list of a plurality ofapplications based on information, the information comprising last usein a period; determining, by the mobile device, a used memory for eachapplication of the plurality of applications; providing, by the mobiledevice, a list of the used memory for a first subset of the plurality ofapplications; and receiving, by the mobile device, a selection of asecond subset of the first subset, wherein the second subset has amountof memory totaling greater than or equal to the anticipated amount ofmemory allocated for the update of the first application.
 9. The methodof claim 8, further comprising deleting the second subset based onreceiving the selection of the second subset.
 10. The method of claim 8,further comprising: deleting the second subset based on receiving theselection of the second subset; and in response to deleting the secondsubset, installing the update of the first application.
 11. The methodof claim 8, further comprising based on the selection of the secondsubset, displaying a remaining memory to be deleted in order to updatethe first application.
 12. The method of claim 8, further comprisingbased on the selection of the second subset adding up to the anticipatedamount of memory allocated for the update of the first application,activating a button for uninstalling the second subset.
 13. The methodof claim 8, wherein the information comprises location of the mobiledevice.
 14. The method of claim 8, wherein the information comprisesfrequency of use in the period.
 15. A computer readable storage mediumcomprising computer executable instructions that when executed by acomputing device cause said computing device to effectuate operationscomprising: receiving, by a device, a notification of an update of afirst application; determining, by the device, an anticipated amount ofmemory allocated for the update of the first application; determining,by the device, a list of a plurality of applications based oninformation, the information comprising last use in a period;determining, by the device, a used memory for each application of theplurality of applications; providing, by the device, a list of the usedmemory for a first subset of the plurality of applications; andreceiving, by the device, a selection of a second subset of the firstsubset, wherein the second subset has amount of memory totaling greaterthan or equal to the anticipated amount of memory allocated for theupdate of the first application.
 16. The computer readable storagemedium of claim 15, further operations comprising deleting the secondsubset based on receiving the selection of the second subset.
 17. Thecomputer readable storage medium of claim 15, further operationscomprising: deleting the second subset based on receiving the selectionof the second subset; and in response to deleting the second subset,installing the update of the first application.
 18. The computerreadable storage medium of claim 15, further operations comprising basedon the selection of the second subset, displaying a remaining memory tobe deleted in order to update the first application.
 19. The computerreadable storage medium of claim 15, further operations comprising basedon the selection of the second subset adding up to the anticipatedamount of memory allocated for the update of the first application,activating a button for uninstalling the second subset.
 20. The computerreadable storage medium of claim 15, wherein the information compriseslocation of the device.